STU 3 Candidate

This page is part of the FHIR Specification (v1.4.0: STU 3 Ballot 3). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions

F.8.1 StructureDefinition: QICore-Device

The official URL for this profile is: 

http://hl7.org/fhir/StructureDefinition/qicore-device

Profile of Device for decision support/quality metrics. Defines the core set of elements and extensions for quality rule and measure authors.

This profile was published on Wed, Mar 11, 2015 00:00+1100 as a draft by Health Level Seven International (Clinical Quality Information - QICore).

F.8.1.1 Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots, and how the XML and JSON presentations work.

This structure is derived from Device.

NameFlagsCard.TypeDescription & Constraintsdoco
.. Device 0..*DeviceItem used in healthcare
... meta ∑0..1MetaMetadata about the resource
... implicitRules ?! ∑0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: IETF BCP-47 (required)
... text I0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... extension 0..*ExtensionAdditional Content defined by implementations
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier 0..*IdentifierInstance identifier
... udiCarrier 0..1IdentifierUnique Device Identifier (UDI) Barcode string
... status ?! S∑0..1codeavailable | not-available | entered-in-error
Binding: DeviceStatus (required)
... type S1..1CodeableConceptWhat kind of device this is
Binding: Device Types (example)
... lotNumber 0..1stringLot number of manufacture
... manufacturer 0..1stringName of device manufacturer
... manufactureDate 0..1dateTimeDate when the device was made
... expirationDate 0..1dateTimeDate and time of expiry of this device (if applicable)
... model 0..1stringModel id assigned by the manufacturer
... version 0..1stringVersion number (i.e. software)
... patient S0..1Reference(QICore-Patient)Patient to whom Device is affixed
... owner 0..1Reference(QICore-Organization)Organization responsible for device
... contact 0..*ContactPointDetails for human/organization for support
... location S0..1Reference(QICore-Location)Where the resource is found
... url 0..1uriNetwork address to contact device
... note 0..*AnnotationDevice notes and comments

doco Documentation for this format

todo

This structure is derived from Device.

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. Device 0..*DeviceItem used in healthcare
... meta ∑0..1MetaMetadata about the resource
... implicitRules ?! ∑0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: IETF BCP-47 (required)
... text I0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... extension 0..*ExtensionAdditional Content defined by implementations
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier 0..*IdentifierInstance identifier
... udiCarrier 0..1IdentifierUnique Device Identifier (UDI) Barcode string
... status ?! S∑0..1codeavailable | not-available | entered-in-error
Binding: DeviceStatus (required)
... type S1..1CodeableConceptWhat kind of device this is
Binding: Device Types (example)
... lotNumber 0..1stringLot number of manufacture
... manufacturer 0..1stringName of device manufacturer
... manufactureDate 0..1dateTimeDate when the device was made
... expirationDate 0..1dateTimeDate and time of expiry of this device (if applicable)
... model 0..1stringModel id assigned by the manufacturer
... version 0..1stringVersion number (i.e. software)
... patient S0..1Reference(QICore-Patient)Patient to whom Device is affixed
... owner 0..1Reference(QICore-Organization)Organization responsible for device
... contact 0..*ContactPointDetails for human/organization for support
... location S0..1Reference(QICore-Location)Where the resource is found
... url 0..1uriNetwork address to contact device
... note 0..*AnnotationDevice notes and comments

doco Documentation for this format

XML Template

JSON Template

todo

 

Other representations of profile: Schematron

F.8.1.2 Terminology Bindings

PathNameConformanceValueSet
Device.language?extrequiredhttp://tools.ietf.org/html/bcp47
Device.statusDeviceStatusrequiredDeviceStatus
Device.typeDevice TypesexampleDevice Types

F.8.1.3 Constraints

IdPathDetailsRequirements
.